Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1643

reference: 966-tree-1
name: 1643
tree-preservation-order: undefined
966-tpo-1
uprn
address-text
point: POINT (-0.994630 50.853580)
geometry: MULTIPOLYGON (((-0.994616 50.853578,-0.994619 50.853583,-0.994626 50.853587,-0.994638 50.853586,-0.994642 50.853584,-0.994644 50.853581,-0.994644 50.853576,-0.994642 50.853573,-0.994630 50.853569,-0.994622 50.853571,-0.994617 50.853575,-0.994616 50.853578)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL